Supervisor history service import manager

ABSTRACT

A system and approach of importing data from site controllers as history imports with a history service by a supervisor in conjunction with a host processor. The history service may reconfigure the history imports to provide the history service virtually full control over the history imports. The history service may runs a history import cycle to ensure that virtually all enabled history imports are performed. The history service may establish a list of history imports to be processed at a beginning of the history import cycle. The history import cycle may query virtually all history imports in an order on a last success time of a history import operation where an oldest time is first on the list. The history service may ensure a maximum number of history imports are running by querying for a count of history imports of an in progress state.

BACKGROUND

The present disclosure pertains to controllers and particularly history service of controllers.

SUMMARY

The disclosure reveals a system and approach of importing data from site controllers as history imports with a history service by a supervisor in conjunction with a host processor. The history service may reconfigure the history imports to provide the history service virtually full control over the history imports. The history service may run a history import cycle to ensure that virtually all enabled history imports are performed. The history service may establish a list of history imports to be processed at a beginning of the history import cycle. The history import cycle may query virtually all history imports in an order on a last success time of a history import operation where an oldest time is first on the list. The history service may ensure a maximum number of history imports are running by querying for a count of history imports of an in progress state.

BRIEF DESCRIPTION OF THE DRAWING

FIG. 1 is a diagram of a history import management arrangement for a controller.

DESCRIPTION

The present system and approach may incorporate one or more processors, computers, controllers, user interfaces, wireless and/or wire connections, and/or the like, in an implementation described and/or shown herein.

This description may provide one or more illustrative and specific examples or ways of implementing the present system and approach. There may be numerous other examples or ways of implementing the system and approach.

A Novar™ Opus™ supervisor may be a target application to provide a present feature. A user of the Novar Opus supervisor may manage and communicate with hundreds or thousands of remote site controllers from a centralized location via an intranet. A site controller may be referred to as an XCM controller or XCM. The XCM in turn may manage and communicate with tens or hundreds of field controllers within the site that perform real-time control of building equipment such as HVAC units, lighting panels, metering and refrigeration circuits.

An existing Opus supervisor may have an ability to pull history data from points being logged with remote site XCM controllers. An approach to perform the pull history data task may be to create within the Opus supervisor application a history import object for each point or group of points. Due to a scale of a customer environment, history data may be pulled from thousands to millions of history import objects. A design of the history import object may be as follows. The object may function as an independent execution unit that functions without regard to its impact on the operating environment, the single Opus supervisor application (process).

The history import object may be configured with a trigger time of day setting which when the time is reached, will initiate the object's action to connect to the remote XCM and begin to transfer new history data from the XCM and write to an Opus SQL server database. This may take several minutes to complete, depending on the host server size and other asynchronous operations within the Opus supervisor process. Typically, virtually all the history import objects trigger times may be configured to trigger randomly over a 24 hour period so that one would not intentionally trigger too many trigger times at the same time. Also, there may be a fault retry timer so that if the point encounters a fault condition, it may be rescheduled to re-trigger the history import again some number of minutes later. An issue that Novar may encounter with this design is that runtime conditions vary, and due to slowing performance of the operating environment, history objects would also slow down, causing more to trigger asynchronously compounding a slow performance condition. Then some history imports may fault resulting in the history import fault retry timer to retriggering the history import again. The result may be that there are so many simultaneous history imports running that the single Opus supervisor process could become un-usable even to the point that it would no longer be communicated with. Also, another compounding factor is that as these failure conditions occur, an importation of new history data may get farther behind causing history imports to take longer to complete contributing to more imports running, simultaneously. Through diagnostic efforts, it appeared to be found that an Opus supervisor process was consuming nearly 100 percent CPU (central processing unit) and large amounts of the host server system memory. The only recourse appeared to kill the Opus supervisor and then restart the supervisor.

The present approach may provide a solution to the stated issue by providing the following product features and the necessary user activities required to use these features. The Opus supervisor may provide a new Opus history service with improved runtime management of the history import operations. A new service operation may be the present feature.

An operational goal of the new Opus history service may be to intelligently manage and control the multiple history import processes ensuring that the history data is collected in a timely manner and at the same time not to allow the imports to overtake host server resources thus causing the Opus supervisor to become unstable or unusable.

The Opus history service will not necessarily replace the history import objects described as central to the issue to resolve. Instead, the service may re-configure the imports so they can be centrally managed by the history service. A first operational action of the service may be to reconfigure the history import objects by disabling the existing invocation timer and retry timer that cause a failure condition. Once the timers are disabled, the service may have full control over the history import objects.

The Opus history service may be designed to run a scheduled history import cycle to ensure that virtually all enabled history imports are performed. Within the cycle, there may be a periodic interval timer allowing the host operational conditions to be monitored, and for the management of the history import objects execution. At the beginning of an import cycle, the service may establish a complete list of history imports that will be processed. The service cycle may initially query for all the history import objects ordering on the last success time of the import operation where the oldest success time is first in the list. This may ensure that the service is always invoking the history importation for the points with the oldest data in the supervisor database ensuring that one eliminates a risk of lost data due to slow performance. Once a cycle is started, the service may then run on a specified interval time. On each interval, the service may ensure that the specified maximum number of history imports is running by querying for the count of imports in an “In progress” state. If the specified number of simultaneous imports is not currently in progress, the service may programmatically invoke a difference ensuring the fixed limits of imports are always running. Once a history import object is invoked to collect history, the history import object may be in the “In progress” state to completion at which time it will return to the idle state. On each execution interval, the service may also read and average the host CPU utilization using the last five readings. If the average host CPU exceeds the specified CPU threshold, then the service may incrementally reduce the number of allowable simultaneous imports directly causing the CPU utilization to reduce. When the average CPU drops below the threshold, the service may incrementally resume up to the specified maximum. Once all the history imports are completed, the cycle may end. A new cycle may be scheduled and the process can be repeated.

Key features may incorporate centralized management of history import operations, continuously run imports at a controlled user definable level, automatic performance tuning by use of CPU monitoring, and ensure that history imports with oldest data are collected first.

The Opus history service may exist in the Opus supervisor services folder. If the service does not already exist, the user may select the service from the Opus history alarm SE module palette and add the Opus history service to the Opus supervisor services. Initially, to configure the Opus history service, the user may set the following operational parameters for the service. An import management enable and/or disable setting may enable the new history import management operation. An import management enable date and time span (optional) may allow a user to specify a date and/or time span when the new history import management operation is enabled. If this operational parameter is not configured, the service may run at all times.

An import management interval time in seconds may be set. This parameter may indicate how often the new history import management can run. When the management runs, the service may recalculate the CPU average and ensure that the correct numbers of imports are running. Max simultaneous imports may be the maximum number of simultaneous imports that the service will allow to run.

A CPU threshold may be where the average host CPU is compared to the CPU threshold value where the service may reduce simultaneous history imports if the average is above this threshold. Number of CPU readings may be a number of CPU readings used in the average compared to the CPU threshold.

The settings of the operational parameters may be configured one time and only adjusted if operational tuning is required for performance concerns. The remaining effort to use the present approach may incorporate standard user activities to join new site XCM controllers to the Opus supervisor. As a new XCM is joined, the history imports required for that XCM may be created and subsequently be available to be managed by a new Opus history service.

In addition to the configuration activities, the Opus history service may provide monitoring views allowing the user to observe operational conditions. These views may incorporate details on the number of running imports, the average CPU and time and date of when a current import cycle started and time and date of when last import was triggered. Also, tabular views of active imports in progress and faulted imports may be available.

Finally, the Opus history service may provide an application programming interface (API) that can allow external applications to query the service for operating statuses. The statuses may incorporate the average CPU and the date and time of the oldest history imported data. The approach may allow an external app to evaluate if the Opus history service is fully loaded and can balance an applied load to ensure optimal performance. This new feature may be added to an existing company (e.g., Honeywell™-Novar™) product by the name of Opus supervisor.

FIG. 1 is a diagram of a history import management arrangement. An invocation timer may cause trigger action. The timer may be represented by a symbol 11. Other items, such as steps or objects represented by a symbol, may be indicated as being at, of, by, or the like of the symbol. The symbol may be a block, square, diamond or another shape.

A question of whether there is a trigger may be asked at a symbol 12. If an answer is yes, then a question of whether there was an enablement may be asked at symbol 13. If an answer is no, then the flow of the diagram may stop at symbol 20. If the answer is yes, then a question whether there is a time enablement may be asked at symbol 14. If an answer is no, then the flow of the diagram may stop at symbol 20. If the answer is yes, then a question of whether there is a start of a new cycle may be asked at symbol 15. If an answer is no, then one may get a current host CPU at a symbol 16. If the answer is yes, then at symbol 17, a list of virtually all history imports may be obtained by oldest last success time first. At symbol 18, a setting of an imports trigger and a retry to a manual (disable) may be set. A max simultaneous import setting may be obtained at a symbol 19. A setting may be made to a runtime max variable at symbol 21. Then at the symbol 16, a current host CPU may be obtained, which may be added to a CPU array at a symbol 22. An average CPU may be calculated at symbol 23. A question at symbol 24 is whether the average CPU is greater than a CPU threshold. If an answer is yes, then a runtime max variable may be reduced at symbol 25 and a number of running imports may be obtained at symbol 28. If the answer is no, then a question whether a runtime max is less than a simultaneous import setting, may asked at symbol 26. If an answer is yes, then the runtime max variable may be increased at symbol 27 and a number of running imports may be obtained at symbol 28. If the answer is no, then just a number of running imports may be obtained at symbol 28. At symbol 29, a question whether a number of running imports is less than a runtime max. If an answer is yes, then a difference of running to runtime max may be calculated at symbol 30 and then next history imports may be invoked to reach the runtime max at symbol 31. A question is whether one at an end of a list of queries history imports may be asked at symbol 32. If an answer is yes, then a history import cycle may be stopped at symbol 33. If the answer is no, then the flow of the present diagram may end at symbol 20.

With regard to the question at symbol 29, if the answer is no, then the question at symbol 32 may be asked with the answer no, thus leading to the end of a flow in the diagram at symbol 20. If the answer is yes to the question at symbol 32, then the history import cycle may be stopped at symbol 33 with a subsequent end of the flow of the present diagram at symbol 20.

To recap, a supervisor history service import manager may incorporate a supervisor, a plurality of site controllers connectable to the supervisor, a plurality of field controllers connectable to each of the plurality of site controllers, and building equipment controlled by the plurality of field controllers. The supervisor may pull history data from the site controllers as history imports. The supervisor may incorporate a history service for runtime management of the history imports. The history service may reconfigure the history imports to provide the history service virtually full control over the history imports by disabling one or more items of a group having an invocation timer and a retry timer. The history service may run a history import cycle to ensure that virtually all enabled history imports are performed. The history service may establish a list of history imports to be processed at a beginning of the history import cycle. The history import cycle may query virtually all history imports in an order on a last success time of a history import operation where an oldest time is first on the list.

The history service may ensure a maximum number of history imports are running by querying for a count of history imports of an in progress state. If a specified number of history imports is not in service, the history service may programmatically invokes a difference to ensure fixed limits of history imports always running.

Once a history import is invoked to collect history, the history import may be in the in progress state to completion at which time the history import may return to an idle state. Upon each execution interval, the history service may read and average last X readings of CPU utilization of a host processor of the supervisor. X may be a numeral equal to or greater than one.

If an average CPU of the last X readings exceeds a pre-determined threshold, then the history service may decrement a number of allowable historical imports to cause the average CPU of the last X readings to decrease. If an average CPU of the last X readings is below the pre-determined threshold, then the history service may incrementally increase the number of allowable historical imports to cause the average CPU of the last X readings to increase.

Upon completion of the history imports, the history import cycle may end. A new history import cycle may be scheduled and the process may be repeated.

The history service may provide monitoring views. One or more monitoring views may be selected from a group having a number of running history imports, an average utilization time of a host processor unit of the supervisor, a time and date of a start of a current history import cycle, a time and date of a trigger of a last history import, and lists of active history imports in progress and faulted history imports.

The history service may provide an application programming interface that permits external applications to query the history service for operating status.

A supervisor history service system may incorporate a supervisor, one or more remote site controllers connected via an intranet to the supervisor, one or more field controllers connected to each site controller, and building equipment connected to each field controller. The supervisor may pull data from points logged with the one or more site controllers. The supervisor may have an application that has a history import for each point or group of points logged with a site controller. The supervisor may incorporate a history service that configures the history imports so as to be managed by the history service. The history service may run a scheduled history import cycle. The history import cycle may have an interval timer.

A list of history imports to be processed by the history service is established at a beginning of the history import cycle.

The history import cycle of the history service may initially query history imports having an order where the history import that has an oldest success time is first on the list which ensures that history importation is for points having oldest data in a supervisor database.

Once a cycle is started, the history service may run on a specified time interval. On each interval, the history service may ensure that a maximum number of history inputs is running by querying a count of history imports in an in progress state.

If the maximum number of history imports is not in process, the history service may programmatically invoke a difference to ensure fixed limits of history imports that are running.

For each interval, the history service may read and average the last readings of utilization of a host processor.

If an average of the X readings of CPU utilization of the host processor exceeds a predetermined threshold, then the history service may incrementally reduce a number of history imports running that causes a reduction of the average of the X readings of utilization of the host processor to the predetermined threshold. If the average CPU of the X readings of utilization of the host processor is less than the predetermined threshold, then the history service may incrementally increase the number of history imports running to cause an increase of the average of the X readings of utilization of the host processor up to the predetermined threshold.

When all of the history imports are completed, the history import cycle may be ended. A new history import cycle may be scheduled to repeat a run of the history service of history imports.

A history service import management mechanism may incorporate a supervisor, site controllers in communication with the supervisor, field controllers in communication with each site controller, and building equipment controlled in real time by the field controllers. The building equipment may incorporate one or more items from a group having heat, ventilation and air conditioning units, lighting panels, metering and refrigeration circuits. The supervisor may pull history data from the site controllers as history imports. The supervisor may incorporate a history service for runtime management of the history imports. The history service may reconfigure the history imports to provide the history service virtually full control over the history imports by disabling one or more items of a group having an invocation timer and a retry timer.

The history service may run a history import cycle to ensure that virtually all enabled history imports are performed. The history service may establish a list of history imports to be processed at a beginning of the history import cycle. The history import cycle may query virtually all history imports in an order on a last success time of a history import operation where an oldest time is first on the list.

The history service may ensure a maximum number of history imports are running by querying for a count of history imports of an in progress state. If a specified number of history imports is not in service, the history service may programmatically invoke a difference to ensure fixed limits of history imports are always running. Once a history import is invoked to collect history, the history import may be in the in progress state to completion at which time the history import may return to an idle state. Upon each execution interval, the history service may read and average last N readings of CPU utilization of a host processor of the supervisor. N may be a numeral equal to or greater than one.

Any publication or patent document noted herein is hereby incorporated by reference to the same extent as if each individual publication or patent document was specifically and individually indicated to be incorporated by reference.

In the present specification, some of the matter may be of a hypothetical or prophetic nature although stated in another manner or tense.

Although the present system and/or approach has been described with respect to at least one illustrative example, many variations and modifications will become apparent to those skilled in the art upon reading the specification. It is therefore the intention that the appended claims be interpreted as broadly as possible in view of the related art to include all such variations and modifications. 

What is claimed is:
 1. A supervisor history service import manager comprising: a supervisor having a central processing unit (CPU) and a database; a plurality of site controllers connectable to the supervisor; a plurality of field controllers connectable to each of the plurality of site controllers; and building equipment controlled by the plurality of field controllers; and wherein: the the CPU connects to the site controllers and transfers history data from the site controllers as history imports to the database; the supervisor comprises a history service for runtime management of the history imports; the history service is configured such that the CPU: disables one or more times of an invocation timer of the history imports and a retry timer of the history imports to reconfigures the history imports and provide the history service control over the history imports; the runs a history import cycle to ensure that virtually all enabled history imports are performed; establishes a list of history imports to be processed at a beginning of the history import cycle and queries the history imports in an order on a last success time of a history import operation where an oldest time is first on the list.
 2. The manager of claim 1, wherein: the history service ensures a maximum number of history imports are running by querying for a count of history imports of an in progress state; and if a specified number of history imports is not in service, the history service programmatically invokes a difference to ensure fixed limits of history imports always running.
 3. The manager of claim 2, wherein: once a history import is invoked to collect history, the history import is in the in progress state to completion at which time the history import returns to an idle state; upon each execution interval, the history service reads and averages last X readings of CPU utilization of CPU of the supervisor; and X is a numeral equal to or greater than one.
 4. The manager of claim 3, wherein: if an average CPU utilization of the last X readings exceeds a pre-determined threshold, then the history service decrements a number of allowable historical imports to cause the average CPU utilization of the last X readings to decrease; and if an average CPU utilization of the last X readings is below the pre-determined threshold, then the history service incrementally increases the number of allowable historical imports to cause the average CPU utilization of the last X readings to increase.
 5. The manager of claim 2, wherein upon completion of the history imports, the history import cycle ends.
 6. The manager of claim 5, wherein a new history import cycle is scheduled and the process is repeated.
 7. The manager of claim 2, wherein the history service provides an application programming interface that permits external applications to query the history service for operating status.
 8. The manager of claim 1, wherein the history service provides monitoring views.
 9. The manager of claim 8, wherein one or more monitoring views are selected from a group comprising a number of running history imports, an average utilization time of the CPU of the supervisor, a time and date of a start of a current history import cycle, a time and date of a trigger of a last history import, and lists of active history imports in progress and faulted history imports.
 10. A supervisor history service system comprising: a supervisor having a central processing unit (CPU) and a database; one or more remote site controllers connected via an intranet to the CPU; one or more field controllers connected to each site controller; and building equipment connected to each field controller; and wherein: the CPU connects to one or more site controllers and transfers data from points logged with the one or more site controllers to the database; the CPU has an application that has a history import for each point or group of points logged with a site controller; the supervisor comprises a history service that is configured such that the CPU: configures the history imports so as to be managed by the history service; runs a scheduled history import cycle that has an interval timer.
 11. The system of claim 10, wherein a list of history imports to be processed by the history service is established at a beginning of the history import cycle.
 12. The system of claim 11, wherein the history import cycle of the history service initially queries history imports having an order where the history import that has an oldest success time is first on the list which ensures that history importation is for points having oldest data in the database.
 13. The system of claim 12, wherein: once a cycle is started, the history service runs on a specified time interval; and on each interval, the history service ensures that a maximum number of history inputs is running by querying a count of history imports in an in progress state.
 14. The system of claim 13, wherein if the maximum number of history imports is not in process, the history service programmatically invokes a difference to ensure fixed limits of history imports that are running.
 15. The system of claim 14, wherein for each interval, the history service reads and averages the last readings of utilization of the CPU.
 16. The system of claim 15, wherein: if an average of the X readings of CPU utilization of the CPU exceeds a predetermined threshold, then the history service incrementally reduces a number of history imports running that causes a reduction of the average of the X readings of utilization of the CPU to the predetermined threshold; and if the average CPU of the X readings of utilization of the CPU is less than the predetermined threshold, then the history service incrementally increases the number of history imports running to cause an increase of the average of the X readings of utilization of the CPU up to the predetermined threshold.
 17. The system of claim 13, wherein: when all of the history imports are completed, the history import cycle is ended; and a new history import cycle is scheduled to repeat a run of the history service of history imports.
 18. A history service import management mechanism comprising: a supervisor having a central processing unit (CPU) and a database; site controllers in communication with the supervisor; field controllers in communication with each site controller; and building equipment controlled in real time by the field controllers; and wherein: the building equipment incorporates one or more items from a group comprising heat, ventilation and air conditioning units, lighting panels, metering and refrigeration circuits; the CPU is configured to connect to the site controllers and transfer history data from the site controllers as history imports to the database; the supervisor comprises a history service for runtime management of the history imports; and the history service is configured such that the CPU disables one or more items of an invocation timer of a history import and a retry timer of the history import to reconfigure the history imports and provide the history service control over the history imports.
 19. The mechanism of claim 18, wherein: the history service is configured such that the CPU: can run a history import cycle to ensure that virtually all enabled history imports are performed; establishes a list of history imports to be processed at a beginning of the history import cycle and queries the history imports in an order on a last success time of a history import operation where an oldest time is first on the list.
 20. The mechanism of claim 19, wherein: the history service ensures a maximum number of history imports are running by querying for a count of history imports of an in progress state; if a specified number of history imports is not in service, the history service programmatically invokes a difference to ensure fixed limits of history imports are always running; once a history import is invoked to collect history, the history import is in the in progress state to completion at which time the history import returns to an idle state; upon each execution interval, the history service reads and averages last N readings of CPU utilization of the CPU of the supervisor; and N is a numeral equal to or greater than one. 